Condition data management

ABSTRACT

A computer-implemented method of managing data includes identifying a plurality of conditions pertaining to a price or a maintenance condition and defining at least one condition selection variant, the condition selection variant representing a plurality of conditions. At least a first key field identifying an item to be associated with at least one of the conditions and is linked to at least a second key field identifying a variable corresponding to the condition. The second key field is displayed to enable data entry by a user to specify the variable corresponding to the price or the maintenance condition pertaining to the item identified in the first key field. The price or the maintenance condition of the item identified in the first key field is determined by processing each condition of the plurality of conditions associated with the condition variant.

FIELD

The present disclosure generally relates to the field of managing data.The present disclosure relates more specifically to management ofpricing and/or maintenance condition data.

BACKGROUND

Management of pricing and other types of data has often been difficultin that an organized structure of pricing or other types of data forsimilar items has been individually maintained, requiring multiplechanges to address a general adjustment to the data. By way of example,prices for many different items are often controlled individually,requiring sales or other general changes to a large number of prices tobe handled separately for individual items. This has often resulted inerrors of incorrect applications of pricing adjustments, or otherchanges to data, meant to apply in general or targeted fashion to aplurality of items. Thus, there is a need to apply a more structuredapproach to management of data for a plurality of items.

SUMMARY

One embodiment relates to a computer-implemented method of determiningpricing. The method includes predetermining a plurality of conditions,each condition defining at least one component of a price andassociating at least two conditions of the plurality of conditions to acondition variant. The condition variant is associated to a product or aservice, and a price of the product or service is determined byprocessing each condition associated with the condition variant. Inanother embodiment, a computer-readable medium may also be provided.

A further exemplary embodiment provides a computer-implemented method ofmanaging data. The method includes identifying a plurality of conditionspertaining to a price or a maintenance condition and defining at leastone condition selection variant, the condition selection variantrepresenting a plurality of conditions. At least a first key fieldidentifying an item to be associated with at least one of the conditionsand is linked to at least a second key field identifying a variablecorresponding to the condition. The second key field is displayed toenable data entry by a user to specify the variable corresponding to theprice or the maintenance condition pertaining to the item identified inthe first key field. The price or the maintenance condition of the itemidentified in the first key field is determined by processing eachcondition of the plurality of conditions associated with the conditionvariant.

A computer-readable medium for use with an electronic device is providedaccording to a further embodiment. The medium has instructionsexecutable using the electronic device for performing a method ofmanaging data. The instructions include predetermining a plurality ofconditions, each condition defining at least one component of a price;associating at least two conditions of the plurality of conditions to acondition variant; associating the condition variant to a product or aservice; and determining a price of the product or service by processingeach condition associated with the condition variant.

A further embodiment provides a computer-implemented method of managingcondition data. The method includes establishing a plurality ofconditions pertaining to an item, each condition relating to thedetermination of a price of the item; assigning a hierarchy level toeach condition; displaying the plurality of conditions and the hierarchylevel assigned to each condition; and automatically determining theprice of the item by the use of at least two conditions of the pluralityof conditions, in accordance with the hierarchy level assigned to eachcondition.

A further embodiment provides a system for determining pricing. Thesystem includes a condition module configured to determine a pluralityof conditions, each condition defining at least one component of aprice; a variant module configured to associate at least two conditionsof the plurality of conditions to a condition variant and associate thecondition variant to a product or a service; and a processing moduleconfigured to determine a price of the product or service by processingeach condition associated with the condition variant.

A further embodiment provides a system for managing data. The systemincludes a condition module configured to identify a plurality ofconditions pertaining to a price or a maintenance condition; a variantmodule configured to define at least one condition selection variant,the condition selection variant representing a plurality of conditions;a key field module configured to link at least a first key fieldidentifying an item to be associated with at least one of the conditionsand at least a second key field identifying a variable corresponding tothe condition; a display to display the second key field to enable dataentry by a user to specify the variable corresponding to the price orthe maintenance condition pertaining to the item identified in the firstkey field; and a processing module configured to determine the price orthe maintenance condition of the item identified in the first key fieldby processing each condition of the plurality of conditions associatedwith the condition variant.

A further embodiment provides a system for managing condition data. Thesystem includes a condition module configured to establish a pluralityof conditions pertaining to an item, each condition relating to thedetermination of a price of the item; a hierarchy module configured toassign a hierarchy level to each condition; a display to display theplurality of conditions and the hierarchy level assigned to eachcondition; and a processing module configured to automatically determinethe price of the item by the use of at least two conditions of theplurality of conditions, in accordance with the hierarchy level assignedto each condition.

A further embodiment provides a system for determining pricing. Thesystem includes means for predetermining a plurality of conditions, eachcondition defining at least one component of a price; means forassociating at least two conditions of the plurality of conditions to acondition variant; means for associating the condition variant to aproduct or a service; and means for determining a price of the productor service by processing each condition associated with the conditionvariant.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram illustrating a data managementsystem according to one exemplary embodiment.

FIG. 2 is a process flow diagram illustrating a method for determining aprice in the data management system of FIG. 1, according to an exemplaryembodiment.

FIG. 3 is a process flow diagram illustrating a method for managing datato determine a price or management condition in the data managementsystem of FIG. 1, according to an exemplary embodiment.

FIG. 4 is a process flow diagram illustrating a method for managingcondition data to determine a price in accordance with a hierarchy levelin the data management system of FIG. 1, according to an exemplaryembodiment.

FIG. 5 is table illustrating schematic representations of conditions forvarious example conditions that may exist in the data management systemof FIG. 1, according to exemplary embodiments.

FIGS. 6 and 7 are schematic representations of a selection area forinput and execution of conditions in the data management system of FIG.1, according to an exemplary embodiment.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

Referring to FIG. 1, a data management system 100 is configured tomanage data and associated conditions related to transactions. Examplesof transactions can include, for example, financial transactions,pricing and providing of goods and/or services. The data managementsystem 100 may manage data and conditions to provide functionality suchas for, by way of non-limiting examples: business aspects/criteriaconsiderations and management, transparency of conditions (e.g.condition spanning), business process management, management for anytype of condition (e.g. procurement area, sales area, etc.), customerspecific plausibility checks, mass condition management possibilities,generic and dynamic condition management tools and features,“user-friendly” application layout and design, etc.

In one example implementation, the system 100 may be used to determineretail prices of a large number of products and services. The system 100may be used to provide different prices among different stores, such asby, for example, using different discounts and different effective timesof the discounts. Differences in transportation and/or storage costs canbe accounted for by increasing prices in the corresponding stores orregions for the same types of goods sold across many stores or regions.Another example of differences in prices is accounting for differentstate sales tax rates.

Although embodiments describing retail products are discussed, thesystem 100 can be used in non-retail applications. Applications can alsoinclude, for example, wholesale applications, inter andintra-organizational cost accounting applications. Examples ofapplications can include providing prices or transaction data for one ormore levels of the distribution chain, including differentiating pricesfor the same types of goods based on a wide variety of variables, suchas geography, supplier, average prices in a store or region and dateranges. Transactions can refer to large items, small items, services andcombinations thereof. A wide variety of pricing types can be used,including, for example, commodity pricing, retail pricing, custompricing, variable discounts, as explained by way of further examplesherein. System 100 can be used in the pricing and selling of servicesincluding financial services, medical services and other services forwhich pricing or other data can be associated.

For purposes of this disclosure, a condition is defined as anyinformation related to a transaction. For example, a condition may be anagreement made on prices, additional charges for a transaction, reducedcharges for a transaction, taxes, etc., which are dependent on variousfactors (e.g., supplier input, customer input, customer group input,supplier offerings, article data, service data, etc.) that are valid fora specific time period.

Data management system 100 generally includes an engine 102, a display104, and a user interface 106. Engine 102 is configured to manage dataand conditions for a transaction according to input on user interface106 and/or predetermined hardware logic or software algorithms. Engine102 includes a condition module 108, a key field module 110, a variantmodule 112, a hierarchy module 114, and a processing module 116. It isunderstood that while engine 102 is shown to contain each module 108-116locally, in other exemplary embodiments, one or more of modules 108-116may be distributed to remote locations, for example servers, andaccessed across a network such as the Internet, a LAN, a WAN, etc. It isalso noted that while each of the modules of engine 102 are shown to beseparate, in other exemplary embodiments any one or more of the modulesmay be combined into a single structure.

Display 104 is configured to give a visual output from engine 102 to auser. According to one exemplary embodiment, display 104 may giveinformation relating to data management as it relates to a transactioninvolving a product or service or any other information that may beavailable to engine 102. In various examples, display 104 may be acathode-ray-tube (CRT) display, liquid crystal display (LCD), plasmadisplay, digital light processing (DLP) display, or any other past,present, or future display technology.

User interface 106 is configured to provide a user with access to engine102. A user may make modifications to data related to a transaction or acondition related to the transaction. A user may wish to view datamanagement information on display 104 and may manipulate user interface106 to make such selections. According to various exemplary embodiments,user interface 106 may be of any past, present, or future design and mayinclude one or more of a tactile touch screen on display 104, a knob, apushbutton, a directional controller, a lever, voice activation, anyother means of control, or any combination thereof. User interface 106may also include a computer-readable media drive to facilitate softwareupdates; uploading of stock, sales, or reallocation information; orother functions loadable from a computer readable medium.

Condition module 108 is configured to identify conditions as they relateto a transaction. Each condition generally defines at least onecomponent of the transaction, for example, a price component (e.g. adiscount, a base price, an additional charge, a tax, etc.) and/or amaintenance condition component (e.g. a plausibility check). It is notedthat some exemplary embodiments, each component may be defined by adifferent condition. For example, in an embodiment that includesmultiple discounts, each discount may be defined by a differentcondition. In an exemplary embodiment that includes a plausibilitycheck, each condition applicable to the price of a product may becompared to determine if there are any logical inconsistencies inapplying the conditions. If there are logical inconsistencies, the usermay be notified via display 104 or another output device. In anotherexemplary embodiment, each of the conditions may be displayed on display104 in a suitable format for viewing by a user, such as in a table.

Key field module 110 is configured to link one or more key fields toeach identified condition from condition module 108. Each key fieldtypically represents a variable that corresponds to a condition. Forexample, a key field of a condition may define an effective datelimitation, a geographical limitation, etc. In one exemplary embodiment,one or more key fields may be specified on display 104 as data entryfields so that a user may manually provide input data (e.g.,corresponding to a price or maintenance condition pertaining to a keyfield) and/or so that the user may verify the key field data. In anotherexemplary embodiment, each condition may be associated with a uniquekey, that is to say a scalar key value that is different from the keyvalues of each other condition, but having at least one charactercorresponding to a condition type. In still another exemplaryembodiment, a key field may identify an item and/or a variable. Forpurposes of this disclosure, an item may be defined as a product,object, or service that data management system 100 is concerned with,for example a stapler, desk, chair, fax machine, etc. if a business wereselling office supplies. A variable may be defined as the content of akey field, for example, if a condition were a discount, the key fieldmay identify a start date, an end date, a geographical region, a percentdiscount, a base price, etc.

Variant module 112 is configured to associate at least two conditionsinto a condition selection variant or condition variant. Each conditionvariant may be associated with a particular product or service asdesired by input from a user on user interface 106 or by a predeterminedalgorithm run by engine 102. For example, a user may wish to create acondition variant of all conditions pertaining to office products, tocleaning services, etc.

Hierarchy module 114 is configured to establish a hierarchy ofconditions by assigning a hierarchy level to each condition. Forexample, one condition may have a higher-ranking condition than anothercondition, which may be lower ranking. Such hierarchy levels may bedefined manually by a user on user interface 106, automatically by apredetermined program running on engine 102, or any combination thereof.The hierarchy levels may also be displayed on display 104 forverification and/or viewing by a user.

Processing module 116 is configured to process data and makedeterminations based on input from modules 108-114 and user interface106. According to one exemplary embodiment where a price is determined,processing module 116 may determine a price of a product or service byprocessing each condition associated with a condition variant. Accordingto another exemplary embodiment, process module 116 may determined aprice for a product or service by the use of at least two conditions inaccordance with the hierarchy level assigned to each condition byhierarchy module 114. For example, in the event of conflicts betweenconditions, the price can be determined by higher-ranking conditionsthat take precedence over lower ranking conditions.

Referring to FIG. 2, a computer-implemented method 200 of managing data,for example, determining pricing, is shown. Method 200 predetermines aplurality of conditions, at step 210. Each condition may define at leastone component of a price. It is noted that in other exemplaryembodiments, method 200 may be implemented on any computer-readablemedium for use with an electronic device that has instructionsexecutable on the electronic device. Method 200 associates at least twoof the conditions to a condition variant in variant module 112 at step220. Method 200 associates the condition variant to a product or servicein variant module 112 at step 230. Method 200 determines a price, step240, of the product or service by processing each condition associatedwith the condition variant in processing module 116.

Referring to FIG. 3 a computer-implemented method 300 of managing datais shown. Method 300 identifies a plurality of conditions pertaining toa price or a maintenance condition in condition module 108 at step 310.Method 300 defines at least one condition selection variant in variantmodule 112 at step 320. The condition selection variant typicallyrepresents a plurality of conditions. Method 300 links at least a firstkey field identifying an item to be associated with at least one of theconditions and at least a second key field identifying a variablecorresponding to the condition in key field module 110 at step 330.Method 300 displays the second key field on display 104 at step 340.This may enable data entry by a user on user interface 106 to specifythe variable corresponding to the price or the maintenance conditionpertaining to the item identified in the first key field. Method 300determines the price or the maintenance condition of the item identifiedin the first key field at step 350. This determination is made byprocessing each condition of the plurality of conditions associated withthe condition variant in processing module 116.

Referring to FIG. 4, a computer implemented method 400 of managingcondition data is shown. Method 400 establishes a plurality ofconditions pertaining to an item in condition module 108 at step 410.Each condition may relate to the determination of a price of the item.Method 400 assigns a hierarchy level to each condition in hierarchymodule 114 at step 420. Method 400 displays the plurality of conditionsand the hierarchy level assigned to each condition on display 104 atstep 430. This may enable data entry by a user on user interface 106 toverify or modify the hierarchy data or other data pertaining to eachcondition. Method 400 automatically determines the price, step 440, ofthe item by the use of at least two of the conditions, in accordancewith the hierarchy level assigned to each conditions.

Referring to FIG. 5, a table 500 illustrates schematic representationsof conditions for various example conditions that may exist in datamanagement system 100. According table 500, the display of theconditions appears in blocks according to condition type. For eachcondition type, each condition in that set or hierarchy may be listed inascending “date from” order, or another order specified by a user may beused. Condition type rows, access level rows, and hierarchy rows areeach marked with different shading for increased clarity. The columns ofthe key fields include all key fields of all condition tables of thedisplayed conditions types. As given in this particular example, onlythe fields presented in white are ready for the input of the respectivechange.

Referring to FIGS. 6 and 7, tables 600 and 700 illustrate schematicrepresentations of a selection area for input and execution ofconditions in data management system 100. The selection area serves forinput and execution of desired conditions. As shown in table 600, a usermay select products or services based on a certain criteria or conditionvariant. Within the selection area, a dropdown list may be available sothat a user may choose between a condition type of a specific selectionand an overlapping condition type selection using condition variants.Table 700 provides further selection options as key fields linked tovarious conditions (e.g., an effective “date from” field) are availablefor selection in a condition variant.

It is important to note that the construction and arrangement of thestock management system as shown in the various exemplary embodiments isillustrative only. Although only a few embodiments of the presentinventions have been described in detail in this disclosure, thoseskilled in the art who review this disclosure will readily appreciatethat many modifications are possible (e.g., variations in sizes,dimensions, structures, shapes and proportions of the various elements,values of parameters, mounting arrangements, use of materials, colors,orientations, etc.) without materially departing from the novelteachings and advantages of the subject matter recited in the claims.Accordingly, all such modifications are intended to be included withinthe scope of the present invention as defined in the appended claims.The order or sequence of any process or method steps may be varied orre-sequenced according to alternative embodiments. In the claims, anymeans-plus-function clause is intended to cover the structures describedherein as performing the recited function and not only structuralequivalents but also equivalent structures. Other substitutions,modifications, changes and omissions may be made in the design,operating conditions and arrangement of the exemplary embodimentswithout departing from the scope of the present inventions as expressedin the appended claims.

As noted above, embodiments within the scope of the present inventioninclude program products comprising machine-readable media for carryingor having machine-executable instructions or data structures storedthereon. Such machine-readable media can be any available media whichcan be accessed by a general purpose or special purpose computer orother machine with a processor. By way of example, such machine-readablemedia can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to carry or store desired program code inthe form of machine-executable instructions or data structures and whichcan be accessed by a general purpose or special purpose computer orother machine with a processor. When information is transferred orprovided over a network or another communications connection (eitherhardwired, wireless, or a combination of hardwired or wireless) to amachine, the machine properly views the connection as a machine-readablemedium. Thus, any such connection is properly termed a machine-readablemedium. Combinations of the above are also included within the scope ofmachine-readable media. Machine-executable instructions comprise, forexample, instructions and data which cause a general purpose computer,special purpose computer, or special purpose processing machines toperform a certain function or group of functions.

It should be noted that although the diagrams herein may show a specificorder of method steps, it is understood that the order of these stepsmay differ from what is depicted. Also two or more steps may beperformed concurrently or with partial concurrence. Such variation willdepend on the software and hardware systems chosen and on designerchoice. It is understood that all such variations are within the scopeof the invention. Likewise, software implementations of the presentinvention could be accomplished with standard programming techniqueswith rule based logic and other logic to accomplish the variousconnection steps, processing steps, comparison steps and decision steps.

1. A computer-implemented method of determining pricing, the methodcomprising: predetermining a plurality of conditions, each conditiondefining at least one component of a price; associating at least twoconditions of the plurality of conditions to a condition variant;associating the condition variant to a product or a service; anddetermining a price of the product or service by processing eachcondition associated with the condition variant.
 2. The method of claim1, further comprising linking a plurality of key fields to eachcondition, each key field representing a variable corresponding to thecondition.
 3. The method of claim 2, wherein, in the act of linking, atleast one key field is an effective date limitation.
 4. The method ofclaim 2, wherein, in the act of linking, at least one key field is ageographical limitation.
 5. The method of claim 1, further comprisingspecifying one or more key fields to display as data entry fields forinput of data by a user.
 6. The method of claim 5, further comprisingreceiving the data from the user corresponding to the one or more keyfields being displayed.
 7. The method of claim 1, further comprisingspecifying one or more key fields to display for purposes of dataverification by a user.
 8. The method of claim 7, further comprisingreceiving input from the user corresponding to the data relating to theone or more key fields being displayed.
 9. The method of claim 1,further comprising associating each condition of the plurality ofconditions to a unique key, the unique key being different from uniquekeys of other conditions, but having at least one charactercorresponding to a condition type.
 10. The method of claim 1, wherein,in the act of predetermining a plurality of conditions, at least onecomponent is a discount.
 11. The method of claim 1, wherein, in the actof predetermining a plurality of conditions, at least one component is abase price.
 12. The method of claim 1, wherein, in the act ofpredetermining a plurality of conditions, at least one component is anadditional charge.
 13. The method of claim 1, wherein, in the act ofpredetermining a plurality of conditions, at least one component is atax.
 14. The method of claim 1, wherein, in the act of determining aprice of the product or service, a plurality of components of the priceare discounts, each of the discounts defined by a different condition.15. The method of claim 1, further comprising displaying the pluralityof conditions in a table.
 16. The method of claim 1, further comprisingreceiving input from a user to specify the at least two conditions to beassociated in the act of associating at least two conditions.
 17. Themethod of claim 1, further comprising establishing a hierarchy ofconditions, wherein, in the act of determining a price, the price can bedetermined by higher-ranking conditions controlling in the event ofconflicts with lower-ranking conditions.
 18. The method of claim 1,further comprising performing a plausibility check, wherein each of theconditions applicable to the price of the product is compared todetermine if there are any logical inconsistencies in applying all ofthe applicable conditions to determine the price; and notifying a userif there are any logical inconsistencies determined in the act ofperforming a plausibility check.
 19. A computer-implemented method ofmanaging data, the method comprising: identifying a plurality ofconditions pertaining to a price or a maintenance condition; defining atleast one condition selection variant, the condition selection variantrepresenting a plurality of conditions; linking at least a first keyfield identifying an item to be associated with at least one of theconditions and at least a second key field identifying a variablecorresponding to the condition; displaying the second key field toenable data entry by a user to specify the variable corresponding to theprice or the maintenance condition pertaining to the item identified inthe first key field; and determining the price or the maintenancecondition of the item identified in the first key field by processingeach condition of the plurality of conditions associated with thecondition variant.
 20. A computer-readable medium for use with anelectronic device, the medium having instructions executable using theelectronic device for performing a method of managing data, the methodcomprising: predetermining a plurality of conditions, each conditiondefining at least one component of a price; associating at least twoconditions of the plurality of conditions to a condition variant;associating the condition variant to a product or a service; anddetermining a price of the product or service by processing eachcondition associated with the condition variant.
 21. Acomputer-implemented method of managing condition data, the methodcomprising: establishing a plurality of conditions pertaining to anitem, each condition relating to the determination of a price of theitem; assigning a hierarchy level to each condition; displaying theplurality of conditions and the hierarchy level assigned to eachcondition; and automatically determining the price of the item by theuse of at least two conditions of the plurality of conditions, inaccordance with the hierarchy level assigned to each condition.
 22. Asystem for determining pricing, the system comprising: a conditionmodule configured to determine a plurality of conditions, each conditiondefining at least one component of a price; a variant module configuredto associate at least two conditions of the plurality of conditions to acondition variant and associate the condition variant to a product or aservice; and a processing module configured to determine a price of theproduct or service by processing each condition associated with thecondition variant.
 23. A system for managing data, the systemcomprising: a condition module configured to identify a plurality ofconditions pertaining to a price or a maintenance condition; a variantmodule configured to define at least one condition selection variant,the condition selection variant representing a plurality of conditions;a key field module configured to link at least a first key fieldidentifying an item to be associated with at least one of the conditionsand at least a second key field identifying a variable corresponding tothe condition; a display to display the second key field to enable dataentry by a user to specify the variable corresponding to the price orthe maintenance condition pertaining to the item identified in the firstkey field; and a processing module configured to determine the price orthe maintenance condition of the item identified in the first key fieldby processing each condition of the plurality of conditions associatedwith the condition variant.
 24. A system for managing condition data,the system comprising: a condition module configured to establish aplurality of conditions pertaining to an item, each condition relatingto the determination of a price of the item; a hierarchy moduleconfigured to assign a hierarchy level to each condition; a display todisplay the plurality of conditions and the hierarchy level assigned toeach condition; and a processing module configured to automaticallydetermine the price of the item by the use of at least two conditions ofthe plurality of conditions, in accordance with the hierarchy levelassigned to each condition.
 25. A system for determining pricing, thesystem comprising: means for predetermining a plurality of conditions,each condition defining at least one component of a price; means forassociating at least two conditions of the plurality of conditions to acondition variant; means for associating the condition variant to aproduct or a service; and means for determining a price of the productor service by processing each condition associated with the conditionvariant.